[metrics] Fix lost connection when metrics query database #3852
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wing2fly
force-pushed
the
metrics_db_conn
branch
from
c831df1
to
b8f5045
Compare
wing2fly
force-pushed
the
metrics_db_conn
branch
from
b8f5045
to
4b76309
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Lost connection happens in Django when using multiprocessing or other parallel execution methods. It often occurs because MySQL connections are not shared safely between processes or threads, leading to disconnections or dropped connections during execution. Metrics use multiprocessing when we started Gunicorn server.
How was this patch tested?
Manually tested on DC cluster
Please review Hue Contributing Guide before opening a pull request.